Related Topics
Flexible Commit Behavior applies to SCORM 1.2 and 2004 Courses. The SCORM 1.2 and 2004 communication framesets use different methods of handling the processing of SCORM elements that are passed to the LearnCenter SCORM API. SCORM 1.2 by default uses a timer based event that elapses every 500 ms to commit SCORM data to the LearnCenter database. SCORM 2004 waits for an explicit Commit() call to commit SCORM data to the LearnCenter database. In SCORM, the LearnCenter can commit information every time an element's value is modified or can wait for an explicit commit call (caching of data). In the event that committing SCORM data on a timely basis is not favorable, the LearnCenter Admin can switch to the other behavior and vice versa. For example, if a SCO is passing interaction data during its quiz module, it might not be favorable in having that information committed every 500 ms in that it generates more traffic, as opposed to just waiting for an explicit Commit call which generates traffic only at one time in the quiz, dependent on how the SCO is developed. The behaviors mentioned can be altered by the LearnCenter Admin to choose any of the two behaviors:
Copyright © 2010-2015, Oracle and/or its affiliates. All rights reserved.